From 3ca0a39fa9e0fc8e803f76b57c234f8687e0c1a0 Mon Sep 17 00:00:00 2001 From: John Ralls Date: Fri, 3 May 2013 16:41:49 -0700 Subject: [PATCH] Bug 606378 - gdk doesn't handle non-main thread rendering on Quartz Document that the restrictions on Win32 apply also to Quartz. --- gdk/gdk.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/gdk/gdk.c b/gdk/gdk.c index 01a4b7a0b3..f1fa0d7461 100644 --- a/gdk/gdk.c +++ b/gdk/gdk.c @@ -666,12 +666,12 @@ gdk_init (int *argc, char ***argv) * * * Unfortunately, all of the above documentation holds with the X11 - * backend only. With the Win32 backend, GDK and GTK+ calls should not - * be attempted from multiple threads at all. Combining the GDK lock - * with other locks such as the Python global interpreter lock can be - * complicated. + * backend only. With the Win32 or Quartz backends, GDK and GTK+ calls + * must occur only in the main thread (see below). When using Python, + * even on X11 combining the GDK lock with other locks such as the + * Python global interpreter lock can be complicated. * - * For these reason, the threading support has been deprecated in + * For these reasons, the threading support has been deprecated in * GTK+ 3.6. Instead of calling GTK+ directly from multiple threads, * it is recommended to use g_idle_add(), g_main_context_invoke() * and similar functions to make these calls from the main thread -- 2.30.2